<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="UTF-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
	<title>Skip rollover | ElasticSearch 7.7 权威指南中文版</title>
	<meta name="keywords" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <meta name="description" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
	<link rel="stylesheet" type="text/css" href="../static/styles.css" />
	<script>
	var _link = 'skipping-rollover.html';
    </script>
</head>
<body>
<div class="main-container">
    <section id="content">
        <div class="content-wrapper">
            <section id="guide" lang="zh_cn">
                <div class="container">
                    <div class="row">
                        <div class="col-xs-12 col-sm-8 col-md-8 guide-section">
                            <div style="color:gray; word-break: break-all; font-size:12px;">原英文版地址: <a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.7/skipping-rollover.html" rel="nofollow" target="_blank">https://www.elastic.co/guide/en/elasticsearch/reference/7.7/skipping-rollover.html</a>, 原文档版权归 www.elastic.co 所有<br/>本地英文版地址: <a href="../en/skipping-rollover.html" rel="nofollow" target="_blank">../en/skipping-rollover.html</a></div>
                        <!-- start body -->
                  <div class="page_header">
<strong>重要</strong>: 此版本不会发布额外的bug修复或文档更新。最新信息请参考 <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html" rel="nofollow">当前版本文档</a>。
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="index.html">Elasticsearch Guide [7.7]</a></span>
»
<span class="breadcrumb-link"><a href="index-lifecycle-management.html">ILM: Manage the index lifecycle</a></span>
»
<span class="breadcrumb-node">Skip rollover</span>
</div>
<div class="navheader">
<span class="prev">
<a href="ilm-with-existing-indices.html">« Manage existing indices</a>
</span>
<span class="next">
<a href="index-lifecycle-and-snapshots.html">Restore a managed index »</a>
</span>
</div>
<div class="chapter">
<div class="titlepage"><div><div>
<h2 class="title">
<a id="skipping-rollover"></a>Skip rollover<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/ilm/ilm-skip-rollover.asciidoc">edit</a>
</h2>
</div></div></div>
<p>When <code class="literal">index.lifecycle.indexing_complete</code> is set to <code class="literal">true</code>,
ILM won’t perform the rollover action on an index,
even if it otherwise meets the rollover criteria.
It’s set automatically by ILM when the rollover action completes successfully.</p>
<p>You can set it manually to skip rollover if you need to make an exception
to your normal lifecycle policy and update the alias to force a roll over,
but want ILM to continue to manage the index.
If you use the rollover API. It is not necessary to  configure this setting manually.</p>
<p>If an index’s lifecycle policy is removed, this setting is also removed.</p>
<div class="important admon">
<div class="icon"></div>
<div class="admon_content">
<p>When <code class="literal">index.lifecycle.indexing_complete</code> is <code class="literal">true</code>,
ILM verifies that the index is no longer the write index
for the alias specified by <code class="literal">index.lifecycle.rollover_alias</code>.
If the index is still the write index or the rollover alias is not set,
the index is moved to the <a class="xref" href="index-lifecycle-error-handling.html" title="Resolve lifecycle policy execution errors"><code class="literal">ERROR</code> step</a>.</p>
</div>
</div>
<p>For example, if you need to change the name of new indices in a series while retaining
previously-indexed data in accordance with your configured policy, you can:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
Create a template for the new index pattern that uses the same policy.
</li>
<li class="listitem">
Bootstrap the initial index.
</li>
<li class="listitem">
Change the write index for the alias to the bootstrapped index
using the <a class="xref" href="indices-aliases.html" title="Update index alias API">index aliases</a> API.
</li>
<li class="listitem">
Set <code class="literal">index.lifecycle.indexing_complete</code> to <code class="literal">true</code> on the old index to indicate
that it does not need to be rolled over.
</li>
</ol>
</div>
<p>ILM continues to manage the old index in accordance with your existing policy.
New indices are named according to the new template and
managed according to the same policy without interruption.</p>
</div>
<div class="navfooter">
<span class="prev">
<a href="ilm-with-existing-indices.html">« Manage existing indices</a>
</span>
<span class="next">
<a href="index-lifecycle-and-snapshots.html">Restore a managed index »</a>
</span>
</div>
</div>

                  <!-- end body -->
                        </div>
                        <div class="col-xs-12 col-sm-4 col-md-4" id="right_col">
                        
                        </div>
                    </div>
                </div>
            </section>
        </div>
    </section>
</div>
<script src="../static/cn.js"></script>
</body>
</html>